Local routing system and method

ABSTRACT

A communication network element determines a service provider&#39;s routing preference for routing communications and routes these communications from an originating connection address to a destination connection address over a network. The communication network element includes a receiver configured to receive a signal, which comprises the originating connection address and the destination connection address. The communication network element also includes a processor that determines the service provider associated with at least one of the originating connection address and the destination connection address of the received signal. The processor also determines the routing preference associated with the service provider using routing data.

CROSS REFERENCES TO RELATED APPLICATIONS

The present application is a continuation of pending U.S. patentapplication Ser. No. 11/391,247, filed on Mar. 29, 2006, which is acontinuation of U.S. patent application Ser. No. 10/900,182, filed onJul. 28, 2004, and issued as U.S. Pat. No. 7,065,193 on Jun. 20, 2006,which is a continuation of U.S. patent application Ser. No. 10/462,786,filed on Jun. 17, 2003, and issued as U.S. Pat. No. 6,795,539 on Sep.21, 2004, which is a continuation of U.S. patent application Ser. No.10/191,419, filed on Jul. 10, 2002, and issued as U.S. Pat. No.6,618,472 on Sep. 9, 2003, which is a continuation of U.S. patentapplication Ser. No. 09/747,940, filed on Dec. 27, 2000, and issued asU.S. Pat. No. 6,442,267 on Aug. 27, 2002, which is a continuation ofU.S. patent application Ser. No. 09/112,384, filed on Jul. 9, 1998, andissued as U.S. Pat. No. 6,205,214 on Mar. 20, 2001, which claims thebenefit of U.S. Provisional Patent Application Ser. No. 60/052,016,filed on Jul. 9, 1997, and U.S. Provisional Patent Application No.60/068,952, filed on Dec. 30, 1997, the disclosures of which areexpressly incorporated herein by reference in their entireties.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is related to an apparatus and method for callrouting within a telecommunications environment. More particularly, thepresent invention relates to an apparatus and method for a local routingsystem enabling a local exchange carrier to route network trafficaccording to a local service provider's preferences.

2. Background and Material Information

Congress enacted the Telecommunications Act of 1996 as part of an effortto foster competition in the local telephone industry. Interpretationsand enforcement of key portions of the Act were placed in thejurisdiction of the Federal Communications Commission. The FCC quicklyset forth regulations which required incumbent local exchange carriers(LECs) to allow competitive local exchange carriers (CLECs, also oftenreferred to as local service providers or LSPs) to utilize the LEC'snetworks to establish a market presence in a region while the CLEC builtits own physical network. The FCC rulings required LECs to make theirnetwork components available using a resale approach in which the CLECpurchases existing service bundles from the LEC and resells thosebundles to the CLEC's customers or an unbundled approach, in which theCLEC purchases individual service components from the LEC, recombinesthose elements in its own (possibly distinct) service bundles, sellsthose rebundled services to its customers, and pays the LEC for theusage of the unbundled components.

A final FCC ruling required LECs to provide the same routing flexibilityfor selected types of calls (local calls, operator calls, and directoryassistance calls) to CLECs as it utilizes for its own service offeringsfor both resale and unbundled customers.

In the existing telephone network, the routing of calls and the billingfor toll charges and usage charges is largely determined by specialtranslations referred to as line class codes (LCCs). LCCs are used toassociate a variety of other translations into a class of service whichprovides a particular local/toll calling scope and specifies wherespecial call types such as operator or directory assistance are routed.The LCCs can also block selected types of calls (900, 1+toll,international, etc.).

The large number of special calling plans, call restrictions, andpermutations of these combinations requires a large number (severalhundred, in most cases) of LCCs to be translated in each LEC switch. Inorder to meet FCC requirements to provide CLECs the same dialing plansoffered by the LEC with alternate routing and/or usage sensitivebilling, existing LCC translations could be duplicated and altered asrequired. However, such an approach would be labor intensive, errorprone, and cost prohibitive. In some cases, attempting to duplicateexisting LCCs would exhaust the serving switch's available supply of LCCtranslations.

To avoid the problems associated with using LCC translations to meet FCCrequirements, a system is need which can re-use existing LCCtranslations to enforce available dialing plans but override the routingof specific call types as requested by a CLEC, and create appropriateusage bill records for calls involving subscribers served by unbundlednetwork elements. Furthermore, it is desirable to perform thisadditional call processing in a centralized system to allow localservice providers to change their preferences without requiring manualchanges in hundreds of decentralized switches.

SUMMARY OF THE INVENTION

In view of the foregoing, the present invention, through one or more ofits various aspects, embodiments and/or specific features orsub-components, is thus intended to bring out one or more of theadvantages as specifically noted below.

A local routing system is provided for selectively routing traffic in atelecommunications network according to a local service provider'spreferences. The local service provider provides service for telephonelines acquired from a local exchange carrier. The telecommunicationsnetwork supports an originator subscribing to the local serviceprovider. The originator initiates a trigger when originating a call toa destination by dialing a number.

The local routing system includes a classifier, a determiner, and arouter. The classifier analyzes the dialed number and categorizes thecall into one of several predetermined classes of traffic. Thepredetermined classes of traffic can be operator assistance traffic,directory assistance traffic, and local traffic. The determinerdetermines whether the local service provider has a routing preferencefor the class of traffic into which the classifier has placed the call.The router routes the traffic to the destination according to the localservice provider's routing preference if a routing preference exists forthe class of traffic into which the classifier placed the call.

According to a preferred embodiment, the local routing system alsoincludes a filter which analyzes the dialed number and determineswhether the call is local. The filter determines whether the call islocal by first comparing an originating local access and transport area(LATA) with a destination LATA, and if the LATAs are identical, thefilter checks whether the destination NPANXX is within the local callingscope of the originator.

According to a preferred embodiment, the determiner determines therouting preference for each switch serving the originator. Furthermore,the local service provider indicates a routing preference for eachswitch within a local service provider network, and for each class oftraffic. In addition, the local service provider may indicate a routingpreference for each line within each switch within the local serviceprovider network. When a routing preference for a line exists, the linerouting preference supersedes the routing preference for the switch.

According to a preferred embodiment, the local routing system alsoincludes a billing generator that generates a billing record for eachunbundled call that is routed according to the local service provider'spreferences. The billing generator may generate a terminating accessbilling record for each unbundled call completed to a subscriber of thelocal service provider. The billing generator may also generate anoriginating access billing record for each unbundled call originated bythe subscriber of the local service provider.

According to a preferred embodiment, the local routing system alsoincludes a switch filter that filters all calls to predeterminednumbers. Consequently, the filtered calls to the predetermined numbersare blocked from the classifier, determiner and router. Therefore, thefiltered calls are routed according to the local exchange carrier'sinstructions.

A billing system is provided for generating billing in atelecommunications network according to a local service provider'susage. The local service provider provides service for telephone linesacquired from a local exchange carrier. The telecommunications networksupports a destination subscribing to the local service provider. Thebilling system includes a terminating trigger initiated by thedestination upon receiving a call, and a billing generator. The billinggenerator generates a terminating access billing record for eachunbundled call completed to the destination subscribing to the localservice provider. In addition, the billing system may include anoriginating trigger initiated by an originator subscribing to the localservice provider upon placing an unbundled call. In response to theoriginating trigger, the billing generator generates an originatingaccess billing record for each unbundled call placed by the originator.

A local routing method is provided for selectively routing traffic in atelecommunications network according to a local service provider'spreferences. The local service provider provides service for telephonelines acquired from a local exchange carrier. The telecommunicationsnetwork supports an originator subscribing to the local serviceprovider. The originator initiates a trigger when originating a call toa destination by dialing a number.

The method includes analyzing, determining, and routing. The analyzingincludes analyzing the dialed number to place the call into apredetermined classes of traffic. The predetermined classes of trafficmay include operator assistance traffic, directory assistance traffic,and local traffic. The determining includes determining whether thelocal service provider has a routing preference for the class of trafficinto which the classifier has placed the call. The routing includesrouting the traffic to the destination according to the local serviceprovider's routing preference, if a routing preference exists for theclass of traffic into which the classifier placed the call.

According to a preferred embodiment, the local routing method alsoincludes analyzing the dialed number to determine whether the call islocal. If the call is not local the traffic is routed to a non-localswitch. It is determined whether the call is local by comparing anoriginating local access and transport area (LATA) with a destinationLATA. If the LATAs are identical, the method also includes checkingwhether a destination NPANXX is within a local calling scope of theoriginator.

According to a preferred embodiment, the local routing method alsoincludes determining the routing preference for the switch serving theoriginator. Accordingly, the local service provider indicates a specificrouting preference for each switch within a local service providernetwork, and a routing preference for each class of traffic. Inaddition, the local service provider indicates a routing preference foreach line within each switch within the local service provider network.When a routing preference for a line exists, the routing preference forthe line supersedes the routing preference for the switch.

According to a preferred embodiment, the local routing method alsoincludes generating a billing record for each unbundled call that isrouted according to the local service provider's preferences. The localrouting method may also include generating a terminating access billingrecord for each unbundled call completed to a subscriber of the localservice provider. The local routing method may also include generatingan originating access billing record for each unbundled call originatedby the subscriber of the local service provider.

According to a preferred embodiment, the local routing method alsoincludes filtering all calls to predetermined numbers, thereby blockingthe filtered calls from being analyzed, classified, and routed accordingto the local service provider's preference. Consequently, the filteredcalls are routed according to the local exchange carrier's instructions.

A billing system is provided for generating originating billing in atelecommunications network according to a local service provider'susage. The local service provider provides service for telephone linesacquired from a local exchange carrier. The telecommunications networksupports an originator subscribing to the local service provider. Thebilling system includes an originating trigger initiated by theoriginator upon placing an unbundled call, and a billing generator. Thebilling generator generates an originating access billing record foreach unbundled call placed by the originator.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is further described in the detailed descriptionwhich follows, by reference to the noted plurality of drawings by way ofnon-limiting examples of preferred embodiments of the present invention,in which like reference numerals represent similar parts throughout theseveral views of the drawings, and wherein:

FIG. 1 illustrates in general block diagram form, an advancedintelligent network (AIN) system for implementing local routing system(LRS) features according to an aspect of the present invention;

FIG. 2 illustrates an exemplary network architecture for LRS forunbundled services (LRU) with one example LSP, according to an aspect ofthe present invention;

FIG. 3 illustrates an exemplary network architecture for LRU with fourexample LSPs, according to an aspect of the present invention;

FIG. 4 illustrates an exemplary-billing only network architecture forLRU with one example local service provider (LSP), according to anaspect of the present invention;

FIG. 5 illustrates an exemplary network architecture for LRS for resoldservices (LRR) with one example LSP, according to an aspect of thepresent invention;

FIG. 6 illustrates an exemplary network architecture for LRR with threeexample LSPs, according to an aspect of the present invention;

FIG. 7 is a message flow diagram showing the message flow betweenvarious components of the AIN network for situations when a 0+ call ismade to an inter-LATA destination having LSP facilities available,according to an aspect of the present invention;

FIG. 8 is a message flow diagram showing the message flow betweenvarious components of the AIN network for situations when a 0+ call ismade to a local destination having LSP facilities available, accordingto an aspect of the present invention;

FIG. 9 is a message flow diagram showing the message flow betweenvarious components of the AIN network for situations when a seven digitlocal call is made to a local destination having LSP facilitiesavailable, according to an aspect of the present invention;

FIG. 10 is a block diagram illustrating the relationship between thecomponents of the system of the present invention for an originatingcall, according to an aspect of the present invention; and

FIG. 11 is a block diagram illustrating the relationship between thecomponents of the system of the present invention for a terminatingcall, according to an aspect of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A local routing system (LRS) is provided which enables an incumbentlocal exchange carrier (LEC) to route network traffic according to alocal service provider's (LSP's) preferences. In a preferred embodiment,the LSP can route operator, directory assistance and local telephonecall traffic depending on which facilities the LSP has established foritself Thus, when the LSP acquires services in addition to the servicesthe LSP has facilities for, the LSP may route network trafficaccordingly. Consequently, the LSP may freely acquire needed unbundledservices or resold services from the incumbent LEC (or another provider)knowing that the network traffic can be properly routed.

Of course, the present invention is not limited to such types of trafficbecause any type of network traffic can be routed according to a serviceprovider's preferences. For example, the system can be modified tohandle interexchange carrier traffic (including directory assistance,operator, etc.) if an interexchange carrier, rather than a local serviceprovider, would like its traffic handled. Also, intra-LATA traffic canbe routed, etc.

Unbundled local switching (ULS) consists of central office switchhardware and software required to permit the transport or receipt ofinformation over the incumbent LEC's local switching network. ULS iscomprised of a ULS port (line or trunk) and originating and terminatingusage. The ULS includes all basic capabilities available to theincumbent LEC (i.e., telephone number, signaling, vertical services,routing, etc.). Unbundled local switching occurs when the LSP buys on apiece-by-piece basis components for operating the service. Exemplarycomponents are the switch, the dial tone, ringing, etc. Unbundled localswitching typically requires billing on a per call basis.

Resale describes reselling an entire service. Typically, a flat rate ispaid for the reselling. Thus, reselling is not usage sensitive and issimply reusing all of the LEC's established equipment including theloop, the switch port, switching capacity, and all features associatedwith the switch port. Resold services are complete services sold to theLSP.

After the LSP obtains telephone services either unbundled or throughresale, the LSP wants to be able to route local traffic to its ownfacilities, if they have the capacity to handle the traffic. Onedifference between resold and unbundled services for the purposes of thepresent invention pertains to billing. For unbundled network services,the LSP must pay a usage fee whereas for resold network services the LSPplays a monthly flat fee independent of usage. Another differencepertains to the fact that LRR only routes local directory assistancetraffic and local operator traffic.

Although local operator and local directory assistance traffic isreferred to throughout this description, the LRS can be easily modifiedto include intra-LATA operator and directory assistance traffic,inter-LATA operator and directory assistance traffic, etc. Similarly thesystem can be modified to handle traffic other than local traffic, suchas inter-exchange carrier traffic.

The LRS of the present invention is designed to handle both types ofservices. Thus, LRS actually encompasses two different systems, LRS forunbundled services (LRU) and LRS for resold services (LRR). Although thetwo systems are similar, they are treated differently because thenetwork handles them differently.

LRS generally operates by analyzing a dialing pattern and called partynumber (CDN) collected from a telephone on one of the LSP's lines. Then,the collected information is classified as a type of traffic.Subsequently, a table look up is performed to determine the LSP'srouting preferences for that type of traffic, and the traffic is routedin accordance with the LSP preferences. Finally, any necessary billingoccurs. The billing information can be utilized to recover toll chargesfor long distance calls, and can also be utilized to charge the LSP fortheir subscriber's use of the LEC's switch port and local network.

The functionality provided by the present invention is invoked bysubscribers obtaining service from a LSP and having the subscriber'sline equipped with special translations (triggers) defined in theserving switch. The triggers required depend upon whether the customer'sLSP is utilizing resold or unbundled network components. With someexceptions (discussed below) subscribers served by LSPs using resoldservices will be equipped with an originating trigger feature which willaccess the LRS logic on outgoing calls or incoming calls forwarded byswitch based features such as call forwarding.

With some exceptions (described below), subscribers served by LSPsutilizing unbundled network components will be equipped with both anoriginating and terminating trigger feature. The originating triggerfeature will invoke the LRS logic on outgoing calls (or forwarded calls)and apply the appropriate custom routing. Because the subscriber isserved by unbundled components, the logic will also force a billingrecord to be generated so the LSP can be billed for the subscriber's useof the switch port. The terminating trigger will invoke the LRS logic toforce the creation of a billing record for any completed incoming callto the subscriber so the LSP can be billed for the switch port usage.

In order to operate, the local routing system of the present inventionrequires special translations called triggers to be assigned within theswitch serving the subscriber requiring custom routing and/or unbundledbilling. For basic types of subscriber ports (e.g., single lines),triggers are assigned as pre-defined features in the serving switch viastandard mechanized provisioning systems. For ports associated withcentrex services and trunk ports, triggers are assigned manually. Onceassigned, the trigger on the subscriber's port accesses the logic in thecentral database using the subscriber's ten digit telephone number as akey into the database.

Exemplary switches which may be utilized to implement the presentinvention are: the Lucent Technologies 1AESS, the Lucent Technologies5ESS, the Ericsson AXE-10, and/or the Northern Telecom (Nortel) DMS-100switches. In a preferred embodiment, the present invention applies toplain old telephone service (POTS) lines and centrex system lines,although LRS can function with any other type of telephone lines, suchas ISDN and multi-frequency PBX systems. Generally, triggers should beapplied on a per telephone number basis.

For switches other than 5ESS primary rate ISDN (PRI), LRU will utilizean off hook delay (OHD) trigger on all switch ports which are being soldon an unbundled basis to LSPs to provide routing service, if desired bythe LSP, and to always create an originating automated messageaccounting (AMA) billing record. For POTS other than 5ESS PRI, LRR willutilize an OHD trigger on all switch ports which are being sold on otherthan an unbundled basis to LSPs to provide routing service, if desiredby the LSP.

Terminating triggers will also be utilized to generate billing for lineusage for LRU. Line ports utilized for POTS will utilize a terminatingattempt trigger (TAT) feature assigned to the line. A trunk port willutilize a ten digit (10D) trigger assigned to all telephone numbers(e.g., direct inward dial (DID) numbers) routed to that trunk port.

Primary rate ISDN (PRI) subscribers utilizing LRS for customized routingrequire trigger translations against the trunk group in order to screenoriginating traffic. Terminating triggers are assigned per existingdirect inward dial (DID) trigger provisioning practices (virtual TAT forDMS, 3/6/10 for 5ESS).

OHD triggers for DMS-100 switches are assigned to PRI trunk groups. Fora 5ESS PRI switch, LRU will utilize a PRI B Channel (PRIBC) trigger onall PRI switch ports which are being sold on an unbundled basis to LSPsto provide routing service, if desired by the LSP, and to always createan originating AMA billing reference. For the 5ESS PRI, LRR will utilizea PRIBC trigger on all PRI switch ports which are being sold on otherthan an unbundled basis to LSPs to provide routing service, if desiredby the LSP.

These POTS trigger requirements mean that LRU's OHD/PRIBC and TAT/10Dtriggers will always exist on all POTS switch ports which are being soldon an unbundled basis to LSPs because of billing. For POTS, LRR'sOHD/PRIBC triggers will only exist if the LSP has active routingservice.

Calling scopes and routing within centrexes are usually controlled byline class codes and/or common block translations which are unique tothe centrex customer. Because, the translations are already unique and aresale approach does not require changes to originating or terminatingbilling, customized routing for resold centrex is more easilyaccomplished by altering the existing line class code and/or commonblock translations for the centrex rather than using the triggerapproach. However, the LRS can be easily modified to operate with AINfor centrex LRR.

Unlike resold centrex, unbundled centrex benefits from the use of AINbecause usage billing must be created for all completed incoming andoutgoing calls, even if the calls are not being custom routed. Threetrigger types are required to invoke the LRS logic for the differenttypes of calls within the centrex environment. The customized dialingplan—access code (CDP-AC) is utilized to invoke LRS on calls which leavethe centrex by dialing access codes associated with local calls (e.g.,dial 9 calls), long distance calls (e.g., dial 8 calls), etc. Thecustomized dialing plan—intercom access (CDP-IC) trigger is used toinvoke LRS on calls to other stations within the same centrex. The TATtrigger is utilized to invoke LRS for incoming calls to stations withinthe centrex. The CDP-AC and CDP-IC triggers are defined within thecommon block translations of the centrex but require database entriesfor each station in the centrex. The TAT trigger is assigned as afeature against each individual station in the centrex, just likestandard non-centrex lines.

Finally, for centrexes that share common dialing plans in a switch, itis necessary to segregate the customers with LRS from those without LRS.For example, if five different centrex customer share a common centrexdialing plan in a switch and one of the five centrex customers becomesan LSP customer with LRS, the centrex customer with LRS must be givenits own dialing plan so as to prevent triggers from being set for thefour remaining centrex customers. Therefore, a trigger calling partyrecord (CPR) for each station within a centrex system must beestablished with a CDP module before the CDP trigger is established in acentrex common block. Translating the trigger without the associatedtrigger CPRs being activated in the ISCP will prevent all stations inthe centrex from originating calls. Specific translations required toestablish a CDP trigger for a given centrex will vary depending upon thecustomer's existing dialing plan.

Custom routing can also be applied to calls originated by two way PBXtrunks, and basic rate ISDN (BRI) trunks by assigning an OHD trigger tothe trunk group.

LRS operates within an advanced intelligent network (AIN) in response tothe triggers described above. Preferably the triggers comply with AINrelease 0.1 OHD and TAT trigger assignment in the AXE-10, DMS-100, 5ESS,and 1AESS switch types. The triggers allow call routing and enablebilling the LSP for both origination and termination. For centrexsystems, the logic is translated with the AIN R0.1 CDP trigger on thestandard centrex access to public facilities and station to stationdialing. For LRR, the logic is translated with the AIN R0.1 OHD triggerfor POTS service. For centrex service the translation is with the AINR0.1 CDP trigger assignment.

The DMS-100 requirements are now discussed. The DMS-100 should be on atleast software release number NA005 to support LRS. Furthermore, theswitch should have AIN specific software release number AIN00018,including AIN automatic callback/automatic call premium feature packageactivated. A table within the switch should be provided which indicatesdigits which will not cause a trigger to occur. Exemplary digits are911, in which case if 911 is dialed, the OHD trigger does not occur. AnAIN database will send a response to the DMS-100 containing the dialednumber as well as an indication of special prefix digits which may havebeen dialed with the number, such as 0+, 10+, 00+, etc. Calls which failto satisfy the dialing plan of the subscriber's line will be screenedprior to encountering the OHD trigger and will reach the standard errorannouncements played by the switch without interacting with the AINdatabase.

The 5ESS switch should be on software release number 5E10 as a minimumin order to support LRS. The AIN database will send a response to the5ESS containing the dialed number as well as an indication of specialprefix digits which may have been dialed with the number, such as 0+,10+, 00+, etc. Seven digit post query calls exist with the OHD and CDPtrigger. Calls which fail to satisfy the dialing plan of thesubscriber's line will be screened prior to encountering the OHD triggerand will reach the standard error announcements played by the switchwithout interacting with the AIN database. Thus, a post query screeningindex is not necessary on the OHD trigger number. In order to screen theincoming digits 911, local digit office dialing can be utilized. If thereceived digits match the digits in the switch, the call proceeds withnormal call processing and an AIN trigger does not occur. Feature accesscodes automatically escape the OHD trigger.

The 1AESS should be on at least software release number 1A12 to supportLRS. The switch must have the call forwarding via private facilitiesfeature loaded. LRS logic in the ISCP is dependent on having operatoridentified in the nature of number (NON) queries from the 1AESS. Thus,the 1AESS requires an operator NON feature in order to include operatoras NON in the query. Some codes such as 911 must be assigned as anescape code to prevent the AIN OHD trigger from occurring within the1AESS. The AIN database will send a response to the 1AESS containing thedialed number as well as an indication of special prefix digits whichmay have been dialed with the number, such as 0+, 10+, 00+, etc. Callswhich fail to satisfy the dialing plan of the subscriber's line will bescreened prior to encountering the OHD trigger and will reach thestandard error announcements played by the switch without interactingwith the AIN database.

For an AXE-10 switch, the switch must have the functionally included insoftware release number L10R7.0 delivery 3, application system 305 inorder for LRS to function. Escape codes should be provided within theAXE-10 switch corresponding to the escape codes utilized at the OHDtrigger. If the received digits match the escape codes, the callproceeds to the normal call processing and the AIN trigger does notoccur. The AIN database will send a response to the AXE-10 containingthe dialed number as well as an indication of special prefix digitswhich may have been dialed with the number, such as 0+, 10+, 00+, etc.Calls which fail to satisfy the dialing plan of the subscriber's linewill be screened prior to encountering the OHD trigger and will reachthe standard error announcements played by the switch withoutinteracting with the AIN database.

When an LSP elects to have an incumbent LEC's AXE-10 route operatortraffic, the AXE-10 requires two routing indexes. One routing index isfor 0-, and the other routing index is for 0+ local and 0+411. Bothrouting indexes may share the same trunk group. The trunk group, at theoption of the LSP, may also be shared with directory assistance traffic.The two routing indexes are required because the post query manipulationof 0− is different than for 0+ local and 0+411 within the AXE-10.

LRS is available to LSPs for both LRR and LRU. However, LRR is onlyoffered on a flat rate basis and therefore does not require anyadditional billing information. All LRU ports, however, require billingto be generated to bill usage to the LSP. The basic AIN billing recordindicates that billing is occurring for LRU. Due to potentialinteractions with other features implementing billing records when LRUis involved, the billing record will be modified when multiple AINservices are encountered on a per call basis. The modified billingrecord indicates what other features are being utilized as well aswhether the originating line is from the LSP or the incumbent LEC, andwhether or not there is terminating usage.

In order to implement LRS, the LSP must identify its routing preferencesfor each of the LEC's offices serving the LSP's subscribers. An IDnumber (or alternate exchange carrier number (AECN)) for the LSP isincorporated into the table name. By including the LSP ID number incertain variables, discussed below, the necessary link between the call,trigger, variables and LSP routing table is provided. In a preferredembodiment, the following fields are provided within the LRS routingtable: the signaling point code (SPC) for each switch which the LSPpurchases LRR or LRU, the office route to which the LSP wants all localoperator calls sent, the office route to which the LSP wants all localdirectory assistance calls sent, the office route to which the LSP wantsall local traffic calls sent (LRU only), and in the case of the AXE-10switch the office route to which the LSP wants all 0-calls sent. Anexemplary LRS routing table is illustrated below in Table 1.

TABLE 1 ROUTING ID #-LSP 1 SPC DESTINATION INDEX (switch #1) 249-019-123OPERATOR 00000123 (switch #1) 249-019-123 DA 00000132 (switch #1)249-019-123 OTHER 00000118 (switch #2) 249-019-126 OPERATOR 00000432(switch #2) 249-019-126 OPM 00000433 (switch #2) 249-019-126 OTHER00000118

If the LSP is only a reseller of lines and does not have LRR, the LSPdoes not have an LRS routing table. Similarly, if an LSP has only ULSports and does not have LRU routing, the LSP will have an LRS routingtable without any entries. Each SSP with LSP defined routes foroperator, directory assistance, or other local traffic has its SPC(which in SS7 terms is the originating point code (OPC) for the AIN R0.1query from the SSP to the ISCP) in the second column of the LSP's LRSrouting table (the first column is only included for illustrativepurposes to correspond the SPC to a specific SSP). The SPC should be inthe LRS routing table once for each type of traffic that the LSP wantsrouted. Thus, the maximum number of times the SPC will occur in an LSP'sLRS routing table is three times. However, in AXE-10 switches theaddition of the 0-(OPM) type makes the maximum four times.

The third column within the LRS routing table is for the destination.Valid entries for the destination column are OPERATOR for 0, 0+ local,and 0+411 operator traffic for the DMS-100, 5ESS and 1AESS switches andfor the 0+ local, and 0+411 operator traffic for the AXE-10 switch; OPMfor 0 operator traffic for the AXE-10 only; DA for directory assistancetraffic; and OTHER for other local traffic.

The last column in the LRS routing table contains the routing index.Valid entries for the routing index column are the 8 digit routing indexwhich conform to the rules for routing indexes that exist for AXE-10,DMS-100, 5AESS and 1AESS switches.

When provisioning LRS, the LSP should also provide: the telephone numberutilizing LRR or LRU, whether LRR or LRU is desired, the local callingscope of the telephone number, and the LRS level, i.e., whetheroperator, directory assistance, local or any combination of these typesof traffic will be routed, or whether only billing occurs.

The local routing system (LRS) is now described with reference to theaccompanying drawings. First, a general description of an advancedintelligent network (AIN) in which the local routing system can beprovided is described.

Many telephone services may be provided using an AIN or AIN type networkwhich permits centralized control of telephone services offered tosubscribers, as opposed to localized control of services at the switchor central office (CO). The AIN system is provided through interactionbetween service switching points and other systems supporting AIN logic.

The AIN based routing system of the present invention may be implementedusing at least AIN Release 0.1 protocol in a public switched telephonenetwork-equipped with SS7 trunk functionality and a service controlpoint (SCP) capable of processing AIN 0.1 queries transmitted via SS7and TCAP (transaction capability application part) protocols. A localdatabase (LDB) and AIN database can be provided by separate platforms,if desired, or by an integrated platform. Each switch serving asubscriber equipped with LRS must have the appropriate SS7 and AINfunctionality configured and active. The AIN based system essentiallyemploys an upper-level software network through the SSPs and the SCP.The upper-level software resides over the service hardware to determinethe routes which the switch will attempt to utilize.

Although the various embodiments of the invention described herein makereference to particular AIN implemented features and structures, otherAIN and AIN type architectures and components may be substituted toprovide and implement the present invention.

Referring now to the accompanying drawings, FIG. 1 illustrates a generalblock diagram of an advanced intelligent network in which the LRS isembodied in accordance with an aspect of the present invention. In FIG.1, local telephone lines 5 connect a plurality of individual networklocations 34A-40B in each geographic area to the closest central office(CO) or end office (EO) 34-40.

End offices 34-40 are equipped as AIN service switching points (SSPs) toallow normal switch call processing to be suspended at specific pointsin a telephone call, enabling TCAP formatted query and response messagesto be transmitted between the SSP and ISCP 30. AIN queries will berouted from a central office or SSP 34-40 to a local signaling transferpoint (STP) 20,22 using existing SS7 links. These queries will then berouted from the local STP 20,22 to the regional STP 24, and from theregional STP 24 to the ISCP 30. The SS7 message routing should bedevised to minimize the need for data administration at the local andregional STPs 20-24. A capability code may be established at the STPs20-24 that serve the ISCP 30. This capability code is utilized by theSSPs 34-40 and the STPs 20-24 to do point code routing until the messageis received by the “last” STP pair (that is, serving the SCP). STPs20-24 within the network are equipped to route AIN SS7 messages fromSSPs 34-40 to ISCP 30 based upon six digit global title translations.For example, the NPANXX of the originating calling telephone number maybe translated by the STP 20-24 to a destination point code (DPC) of theISCP 30 running the LRS.

The SSPs 34-40 may include, but are not limited to, AXE-10, 5ESS, 1AESS,and DMS-100 switches. The trigger on the 5ESS switch may be an AIN typeOHD trigger, although more specific trigger requirements are discussedelsewhere. The trigger may be based upon AIN Release 0.1 protocol, andpreferably AIN Release 0.1 query variables are utilized by a callprocessing record (CPR) 10 in the ISCP 30 to determine call routing.

Triggers in switches may have certain identifiable parameters, includingthe telephone number with the trigger, that permit the SSP 34-40 andISCP 30 to synchronize their mutually supporting activities. On its end,the ISCP 30 utilizes the trigger identifiable parameters to select theproper CPR to implement the call routing

For purposes of illustration, four SSPs are shown in FIG. 1. The actualnetwork may be provisioned with more (or less) than the number of SSPsshown in FIG. 1. The SSPs 34-40 are switches which perform the followingfunction: recognize AIN-type calls; launch queries to the ISCP 30; andreceive commands and data from the ISCP 30 to further process and routeAIN-type calls. When one of the SSPs 34-40 is triggered by an AIN-typecall, the SSP formulates an AIN service request and responds to callprocessing instructions from the network element in which the AIN logicresides. The AIN logic or control software may reside in a database at aservice control point (SCP) 26. The SSPs 34-40 are connected by trunkedcommunication lines 52 which connect and carry communications, e.g.,voice and/or data, from a calling party to a called party.

In FIG. 1, the SSPs are shown equipped with common channel signaling(CCS) capabilities, e.g., signaling system 7 (SS7), which provides fortwo-way communications of data messages between each SSP 34-40 and theISCP 30 via CCS links 50. The data messages are formatted in accordancewith the transaction capabilities applications part (TCAP). As shown inFIG. 1, each SSP 34 and 36 may be connected to a first local area STP 20by SS7 link 50; and each SSP 38 and 40 may be connected by SS7 link 50to STP. The connections by links 50 to the STPs 20-24 are for signalingpurposes, and allow the SSPs 34-40 to send and receive messages to andfrom the ISCP 30 via the STPs 20-24. Each of the STPs 20-24 can beconnected to a large number of other STPs. For purposes of illustrationin FIG. 1, SS7 links 50 are shown as connecting local STPs 20, 22 to aregional STP 24, and connecting the regional STP 24 to the ISCP 30.

The ISCP 30 is an integrated system which may include a servicemanagement system (SMS) 27, a data and reports system (DRS) 28, aprogrammable service control point (SCP) 26, and a service creationenvironment (SCE) 25, such as Bellcore Service Provisioning and CreationEnvironment Network Element (SPACE). The SCE 25 is a software basedterminal that may be implemented to work with the SMS 27 to create,modify, and load service control software (i.e., logic) into thedatabase in the SCP 26. The SCP 26 executes software-based logic and mayreturn call routing instructions to the SSPs. The SMS 27 is provided toprovision customer CPRs and data. The DRS 28 may be provided forcompiling calling information to be utilized for billing andadministrative purposes. By way of example, the ISCP 30 may beimplemented with the Bellcore Integrated Service Control Point (ISCP),loaded with preferably at least ISCP software version 5.0.7, availablefrom Bell Communications Research, Inc., of Livingston, N.J.

The SCP 26 may be linked to a local database (LDB) 54 that storesvarious routing information, e.g., information for determining whether acalled number is local or toll. The local database 54 preferably resideswithin the ISCP 30.

AIN call processing differs from standard telephone call processing inthat a query to a centralized database, e.g., ISCP 30, is triggered byan AIN application. In AIN type call processing, an SSP is responsiblefor identifying calls associated with AIN services, detecting whenconditions for AIN service involvement are met, formulating servicerequests for call processing instructions, and responding to theinstructions received. With AIN call processing, the call may besuspended at the calling party's end office or switch equipped as an SSPand may send a data message, via the SS7 links, to the STPs to establishthe call route. AIN services are created by assigning appropriate SSPcall suspension points, known as AIN “triggers”, accessed via customerlines or telephone numbers, and accessing customer or service specificlogic in the ISCP 30. The SSPs launching the AIN queries are preferablyend office AIN SSPs, 34-40.

For purposes of illustration, assume that a customer at location 34Adesires to call a business having a main office at 36B. The customerpicks up the receiver at 34A and gets a dial tone from SSP 34. Thecustomer may dial the telephone number of the business, e.g., 987-6543,from originating location 34A, ultimately offering connection to theoffice of the business, e.g., location 36B. The AIN trigger may beestablished in the SSP originating end office that serves the NXX of thecaller, i.e., end office 34. In FIG. 1, SSP 34 receives the call and istriggered. As a result, SSP 34 launches a message, over links 50, toquery SCP 26. SCP 26 then responds back to SSP 34 with routinginformation, and SSP 34 routes the call over trunks 52 to SSP 36. SSP 36rings location 36B, and the business at location 36B may answer tocomplete the communication path.

Upon receiving the query message from the AIN SSP equipped end office34, the ISCP 30 executes software based logic programs stored in the SCP26 to perform subscriber functions, e.g., determining routinginformation based upon the LSP's preferences, and returns a response tothe end office 34 with call routing instructions to forward the callappropriately. The AIN service application, e.g., CPR 10, may be storedin an ISCP database, e.g., the SCP 26, and accessed by a predeterminedSSP query launched from the triggering location, e.g., location 34. TheCPR 10 contains the logic for each trigger necessary to effectappropriate call routing.

When the ISCP 30 receives a query, the advanced intelligent LRS routinglogic will be executed. Call data may be collected and recorded in theDRS 28, as per the normal ISCP measurement node operation. For example,the ISCP 30 may contain resident service software that collects ISCPusage data.

After the ISCP 30 has collected the call data, the ISCP 30 returnscontrol of the call to the call suspending SSP, with proper routinginformation, for completion (i.e., routing). Once the logic has beencompleted, control of the originating call returns to the triggeringSSP.

The trigger CPR requires some provisionable variables. A service typevariable is necessary to indicate whether a telephone number is an LRSsubscriber. The service variable typically has only two possible values:R signifying the telephone number is an LRR subscriber and U signifyingthe telephone number is an LRU subscriber. The service variable cannothave a value permitting both LRR and LRU to exist at the same time, asthey are mutually exclusive.

Another provisionable variable indicates the LSP for a particulartelephone number. The LSP variable facilitates billing and determiningwhich LRS routing table is utilized.

A calling scope variable is necessary to indicate a dialing plan for thetelephone number which uniquely identifies a local call scope. The valueof the calling scope variable enables determining which local databasedialing plan to utilize for local versus intra-LATA toll determinations.

The LRS system of the present invention is capable of working with hostand remote switches. Consequently, another provisionable variablerequired is the remote point code variable. The remote point codevariable is utilized for subscribers served by certain 5ESS remoteswitches equipped with direct trunk groups, and other remote switcheswhich do not uniquely distinguish the remote from its host in theoriginating point code value sent with an AIN query. The remote pointcode variable can be utilized to override the host point code sent inqueries, and facilitates selecting the desired routes in the remoteswitch. For most subscribers, this variable will contain all zeroes(000-000-000) which will cause the originating point code of the AINquery to identify the routes for that LSP in the subscriber's switch. Ifthe subscriber is served by a 5ESS remote switch with direct trunks,using the originating point code would cause trunks from the hostswitch, instead of the remote switch, to be selected. The remote pointcode variable, if set to something other than 000-000-000, is utilizedto select routes for the remote switch and override the routesassociated with the host switch.

Another provisionable variable is the LRS level variable which controlsthe line level routing option permitting a specific LSP line to havedifferent operator, directory assistance, and local traffic routing. Ina preferred embodiment, the default value of the LRS level variable iszero. Because an unbundled line may exist without routing, the value ofzero only applies to LRU which still requires billing. For LRR, nodefault value is necessary because customized routing is required (i.e.,no billing occurs). When the value of the LRS level variable directs thesystem to perform routing for a service such as directory assistance,and no routing has been defined for the LSP at the end office servingthe line, default LRS logic performs routing to the LEC facilities.However, for the 1AESS switch type, even the LEC handling of theoperator traffic must be in the LRS table. Alternatively, theinformation can be in a table within a feature interaction manager (FIM)(discussed below). When the value of the LRS level variable indicates aroute, e.g., OTHER, that does not exist at the LSP level for that endoffice, LRS logic will utilize incumbent LEC routes for that type oftraffic regardless of whether the traffic is operator, directoryassistance, or local traffic. According to a preferred embodiment,possible values for the LRS level variable are shown in the Table 2below.

TABLE 2 Value Definition Applicability LRU Applicability LRR 0 No CustomRouting X N/A 1 Operator Only X X 2 Directory Assistance X X Only 3Operator and Directory X X Assistance Only 4 Local Traffic X NA 5Operator and Local X NA Traffic Only 6 Directory Assistance X NA andLocal Traffic Only 7 Operator Directory X NA Assistance and LocalTraffic

Whenever a lookup in the LRS routing table is required, the LRS levelvalue is first checked to determine whether the lookup is necessary. Forexample, when telephone one number 512-372-5450 has an LRS level of two,and the logic indicates a lookup in the LRS routing table for a localrouting index should be made, the lookup will not occur because the LRSlevel of two does not include local traffic. However, when the telephonenumber 512-372-5450 has an LRS level of twos and the logic indicates alookup in the LRS routing table for a directory assistance routingindex, the lookup occurs because an LRS level of two includes directoryassistance traffic.

Three additional provisionable variables are also provided in thetrigger CPR for a telephone number with LRU for direct inward dial (DID)customers. DID is a trunk related terminating service and is thereforenot an issue for LRR. First, a provisionable variable is necessary toindicate whether or not the telephone number is part of a DMS-100 DIDtrunk group. If the telephone number is part of a DMS-100 DID trunkgroup, an additional variable should be provided to indicate whetherseven or ten digits is required for that DMS-100 DID trunk group.Finally, a variable should be provided which indicates the route indexto the DID trunk.

Traffic is defined as three types in a preferred embodiment: operator,directory assistance, and local. Operator traffic includes callsoriginated by dialing 0, 0+telephone number and 0+411. Directoryassistance traffic includes calls originated by dialing 1+411, and ahome NPA+555-1212. The home NPA is the NPA of the calling party. Forexample, if 314-235-1234 dials their home NPA directory assistance, theywould dial, 314-555-1212. Local traffic includes all calls to anothertelephone number which do not incur any toll charges. Thus, local isdefined to be those calls within the free calling scope of theoriginating NPANXX. In another embodiment, local traffic also includescalls which are free due to optional calling plans.

Thus, LRS is an optional service which enables LSPs to route trafficaccording to the LSP's preferences. Furthermore, an LSP may purchase LRSonly for the traffic type desired. For example, LSP 1 may decide tohandle operator and directory assistance and not local traffic, whereasLSP 2 can decide to handle only local traffic. It is important to notethat the other end of trunk groups carrying any type of traffic from theLEC's switch must terminate on facilities other than the LEC'sfacilities. Thus, it is an option for LSP 1 to route the traffic to anoperator system, directory assistance system, or switch owned by someoneother than the LSP, but the traffic cannot be routed back to the LEC'sswitch. If an LSP does not employ LRS at all or does not employ LRS forone or more traffic types, the LEC will by default, route the LSP'slocal traffic like it does its own local traffic, and bill the LSPaccordingly.

It is possible for an LSP to employ LRU and LRR simultaneously, but anyparticular line may only have LRR or LRU. The LSP should utilize adifferent alternate exchange carrier number (AECN) for LRU and LRR.

For a given SSP, an LSP may share the same operator and directoryassistance routing for both LRU and LRR. (The local routing is exclusiveto LRU.) Thus, the operator and directory assistance traffic can share atrunk group at the LRS subscriber's option as both are multi-frequency(MF) with an operator signaling trunk group type known as modifiedoperator service signaling (MOSS). However, it is not possible tocombine local traffic with either operator or directory assistancebecause local traffic flows through SS7 trunks. In addition, an LSP mayset a route for a SSP and prevent the route from being utilized bysetting an alternative route at the line level. For example, all LRUcustomers of the LSP can have a line level that permits routing to theroute set in the SSP (e.g., the LSP's facilities) while all LRRcustomers of the LSP in the same SSP can have a line level that routesthe call elsewhere (e.g., to the LEC system). In another example an LSPhas one business line and one residence line. The LSP could have thebusiness line sent to the LSP operator and the residential line sent tothe LEC operator.

LRS interacts with existing translations utilized to route callsoriginated by the LSP subscriber. After allowing the switch to performthe appropriate pre-query screening to block incorrectly dialed calls,LRS augments the routing of the selected classes of traffic by selectingroutes specified by the LSP, instead of routes derived from the switchbased line class code. The design allows LSPs to utilize LSP routes insome switches, and incumbent LEC routes in other switches by providingor omitting overriding route information, as desired for each switch.Thus, the intent is for LSPs to utilize existing LEC local networkfunctionality without chance when it comes to call processing unless theISCP includes a route index in the response to the switch.

The OHD trigger is utilized for most originating call scenarios. A TATtrigger is utilized for most terminating call scenarios. The OHD triggeranalyzes the dialing party and called party number to determine if arouting index should be returned. The OHD trigger also causes anautomatic message accounting service logic program identification(AMAslpID) parameter to be returned along with other billing informationto the SSP. The SSP then generates a billing record for the originatingunbundled call. The TAT trigger will only cause an AMAslpID to bereturned along with other billing information to the SSP.

For centrex, the OHD, custom dialing plan access code (CDP-AC), andcustom dialing plan intercom code (CDP-IC) triggers are utilized for allLRS originating call scenarios. This specific trigger varies by switchtype and by originating call scenario, e.g., station to station,9+escape code to outside the centrex, etc. For LRU, the TAT and 10Dtrigger is utilized for terminating call scenarios. The OHD, CDP-AC andCDP-IC triggers are utilized to analyze the dialing pattern and CDN todetermine if a routing index should be returned. The OHD trigger causesan AMAslpID to be returned along with other billing information to theSSP. The SSP generates a billing record for the originating unbundledcall. The TAT and 10D trigger only causes an AMAslpID to be returnedalong with other billing information to the SSP.

Referring now to FIG. 2 an exemplary network architecture for LRU withone LSP is described. The local STP 20 is connected to multiple endoffices/SSPs 31-34, 36, 37 via SS7 links which allow SS7 protocolsignaling. Although FIG. 1 shows four end offices 34-40, a network isnot limited to only those end offices shown, thus, FIG. 2 shows six endoffices 31, 32, 33, 34, 36, 37. In FIG. 2 the end office, SSP 34, isshown more specifically as a Lucent Technologies 1A Electronic SwitchingSystem (1AESS) switch and the end office/SSP 36 is shown morespecifically as an Ericsson AXE-10 digital switch. End office 31 isshown as a Nortel digital multiplex system (DMS) 100/200 trafficoperating position system (TOPS), end office/SSP 32 is shown as a NortelDMS 100 switch, and end office/SSP 33 is shown as a Lucent Technologies5ESS switch. Further, end office/SSP 37 is shown as the switch forhandling local traffic for the new LSP 1. IXC switch 35 is shown as aninterexchange carrier (IXC) switch.

Each of the switches 31, 32, 33, 34, 36 is shown connected via an analogline 5 to a telephone 31A, 32A, 33A, 34A, 36A. The DMS 100/200 TOPSswitch 31 is also provided with the LEC's toll assistance and directoryassistance operator system 31B. Each of the LEC's switches 32, 33, 34,36 are connected to the DMS 100/200 TOPS switch 31 with multi frequencytrunks with operator signaling, and from the DMS 100/200 TOPS switch 31to the LEC's switches 32, 33, 34, 36 with an SS7 trunk. A two-way SS7local trunk such as a GR-317 also runs between the DMS 100/200 TOPS, andeach of the LEC's switches 32, 33, 34, 36. Each of the LEC switches 32,33, 34, 36 is also connected to the IXC switch 35 with an SS7 trunk suchas a GR-394. Each of the incumbent LEC switches 32, 33, 34, 36 is alsoconnected to a storage facility 32C, 33C, 34C, 36C where the originatingand terminating AMA records for the unbundled local switching can bestored and sent to downstream systems for billing purposes. A storagefacility 31C may also be attached to switch 31, however, it is not shownin the drawings. Furthermore, switch 31 can be connected to switch 37and systems 56, 58 in the manner that switches 32, 33, 34, 36 areconnected. To keep the drawing from becoming overly cluttered, theseconnections are not shown.

In addition to the switch 37 of the new LSP 1, in the example shown inFIG. 2, LSP 1 also has its own operator system 56 and directoryassistance system 58. Thus, in the example shown in FIG. 2, LSP 1 iscapable of handling directory assistance traffic, operator traffic andlocal traffic. Accordingly, the operator system 56 and the directoryassistance system 58 are connected with multi frequency trunks withoperator signaling to each of the incumbent LECs switches 32, 33, 34,36. Thus, each of the LEC switches 32, 33, 34, 36 is able to routeoperator and directory assistance traffic to LSP 1 via multi frequencytrunks with operator signaling and to the LSP 1 switch 37 via SS7 localtrunks for local traffic.

In this example, the LRU network architecture is able to handle-complexdialing plans, multiple classes of service, and feature interactionbetween LRU, and switch based and AIN services. The system sorts throughthe possibilities and connects operator, directory assistance, and localcalls to the proper trunk groups on an LSP by LSP basis.

FIG. 3 shows a situation in which four new LSPs have acquired unbundledlines from the incumbent LEC which is shown with three end offices 32,33 and 34. For the example shown in FIG. 3, LSP 1 handles its ownoperator, directory assistance and local traffic. LSP 2 utilizes LSP 1'sdirectory assistance system, and does not require routing for operatoror local traffic. LSP 3 routes only local traffic, and utilizes theincumbent LECs directory assistance and operator facilities fordirectory assistance and operator services. LSP 4 handles its ownoperator and directory assistance traffic and utilizes a single trunkgroup for the routing of both operator assistance and directoryassistance traffic. Thus, as shown in FIG. 3, the incumbent LEC switches32, 33, 34 each have a connection to LSP 1's switch 37, LSP 1's operatorsystem 56 and LSP 1's directory assistance system 58. In order to routeLSP 2's directory assistance traffic, a separate line connects LSP 1'sdirectory assistance system 58 and each of the incumbent LECs endoffices 32, 33, 34. LSP 3 has a link connecting each of the LEC's endoffices 32, 33, 34 to LSP 3 switch 60 enabling local traffic to berouted to LSP 3's facilities. LSP 4 is shown with a combined operatorand directory assistance system 62, and consequently has a single trunkconnection to each LEC end office 32, 33, 34. Each LEC switch 32, 33, 34is also connected with each other LEC switch 32, 33, 34.

For situations when an LSP only requires billing from the incumbent LEC,a network architecture such as that shown in FIG. 4 may be implemented.In other words, FIG. 4 shows the LRU network architecture for an LSPhandling none of the three traffic types. FIG. 4 is similar to FIG. 2except that no LSP 1 switch, LSP 1 operator system, or LSP 1 directoryassistance system are provided. Although an LRU billing only system doesnot have any trunk groups associated with it (nor routing indexes), thesystem should be provisioned just like an LRU system with routing toenable easy implementation when the LSP becomes a user of LRU withcustom routing.

FIG. 5 shows an exemplary network architecture for LRR. FIG. 5 issimilar to FIG. 2 except that no storage for billing records 32C, 33C,34C, 36C is necessary because no billing records are generated for LRR.Moreover, LRR does not support local traffic routing, therefore no LSP 1switch is required.

FIG. 6 shows an exemplary network architecture for LRR with three LSPs.LSP 1 handles its own operator and directory assistance traffic, LSP 2has its directory assistance traffic routed to LSP 1's directoryassistance system and LSP 3 handles its own operator and directoryassistance traffic. LSP 3 utilizes the same trunk group for both typesof traffic. Thus, end offices 32, 33, 34 of the incumbent LEC have trunkconnections to LSP 1's operator system 56 and LSP 1's directoryassistance system 58. Each LEC end office 32, 33, 34 also has anadditional trunk connection to LSP 1's directory assistance system forrouting of LSP 2's directory assistance traffic. Each of the LEC endoffices 32, 33, 34 has a single trunk connection to LSP 3's operator anddirectory assistance system 63. Finally, each LECs end office isconnected with the other LEC end offices, i.e., end office 32 has atrunk connection to end office 33 and 34, and end office 33 has a trunkconnection to end office 32 and end office 34.

According to a preferred embodiment, LRS is compatible with line relatedand trunk related switch based features such as call waiting, callforwarding, speed calling, direct inward dial (DID), etc.

For centrex systems, station to station calls will not trigger LRSexcept for LRU, which requires originating billing to be generated. Whenthe 9+escape code to an outside line is handled by the ISCP, LRS acts asif the 9+ did not exist and the OHD logic is applied. These 9+ calls arediverted to the operator, directory assistance or local facilities whennecessary. Of course, if LRU applies to the call, then an originatingbilling record is also generated.

Because LRS is only applied to local calls, a filtering function isapplied to distinguish local calls from intra-LATA toll, inter-LATAtoll, and international calls. International calls can be identifiedthrough the nature of number (NON) associated with the called number(CDN). Inter-LATA calls can be identified through the NON associatedwith the CDN, and the use of an ISCP supported NPANXX table. The tablemaps each NPANXX to a specific LATA. If necessary, the table can beutilized twice, once to get the LATA of the calling party number (CPN)and once to get the LATA of the CDN. However, the LATA of the CPN shouldcome up in the query from the SSP to the ISCP, and only one lookup istypically required. If the LATAs are not the same, the call isdetermined to be an inter-LATA call.

Local and intra-LATA toll calls are not so easily distinguished. CDNswith seven digits and a NON of subscriber can be treated as local.However, ten digit local dial plans also exist. In fact, the only localdial plan for 0+ is ten digits. Furthermore, NPA splits in overlays andmajor market areas have led to the use of more ten digit local dialplans. The NON for all ten digit dialing is national so NON is not anadequate discriminator between local, intra-LATA toll or inter-LATA.

According to a preferred embodiment of the present invention, a localdatabase (LDB) can be utilized to define all valid local call scopes foran originating NPANXX. Every originating NPANXX has an associated localcalling scope. Furthermore, optional local calling scope plans may existto which a line and an NPANXX may subscribe. If a line does subscribe tosuch a plan, the NPANXXs that the line can reach from the originatingNPANXX are predefined for the plan. Thus, LRS will utilize the LDB whennecessary to discriminate between local and intra-LATA calls that aredialed with ten digits. The database contains the local calling scopefor every NPANXX. Thus, a simple lookup will be able to determinewhether the call is local or intra-LATA toll.

FIG. 7 shows the call flow of a 0+ call to an inter-LATA destination.The calling party 314-235-0789 dials 0+816-342-1111. The SSP 34 collectsthe originating number and dialed number, determines the nature ofnumber and passes the information on to the ISCP 30. The ISCP 30determines that the traffic type is operator traffic and that the callis inter-LATA. Therefore, LRS is inapplicable. The ISCP 30 generatesbilling information and tells the SSP 34 to contact the inter-exchangecarrier switch 35 which establishes a connection with the destinationnumber to result in the final talk path as shown in FIG. 7.

FIG. 8 shows the call flow of a 0+ call to a local destination with LSPfacilities for handling operator calls. The same calling number as shownin FIG. 7 calls 0+314-521-1365. The SSP 34 collects information similarto the information collected in FIG. 7, and forwards the information tothe ISCP 30 which determines that the call is an intra-LATA call due tothe identical NPAs. The ISCP 30 then sends the dialing plan number ofthe calling party, the calling party ID, and NPANXX of the called partyto the LDB 54 which determines whether or not the call is local. In theexample shown in FIG. 8, the call is determined to be local causing theISCP 30 to forward a routing index to the SSP 34 along with the billinginformation. The SSP 34 then routes the call to the LSP operator system56 via a MOSS connection establishing the final talk path from thecalling party to the LSP operator system 56. The LSP operator thenhandles the operator call.

In FIG. 9 calling party 314-235-0789 dials the telephone number636-0952. The SSP 34 forwards the calling party's number, the calledparty number, and the NON to the ISCP 30 which determines that the callis a local call due to the seven digit called number. The ISCP 30 thenforwards the routing index for local calls (because the LSP has its ownlocal facilities) to the SSP 34 along with other AMA billinginformation. The SSP 34 then routes the call to the LSP switch 37 whichconnects the call establishing a final talk path between the callingparty 34A and the LSP switch 37.

In order to implement LRS within the ISCP 30, two levels must beestablished. The first level is the LSP level and the second dependentlevel is the line level. The LSP level is a table of data utilized bythe line level. The purpose of the LSP level is to consolidate all SSProuting indexes for operator, directory assistance, and local trunkgroups that support LRS into one location to simplify provisioning andease maintenance. Due to consolidation, an existing routing index can bechanged without disrupting the service. Consolidation also allows arouting index to be either added or removed from all lines of an SSP atthe line level in one non-disruptive step. The LSP level is implementedwith the LSP table described above. Preferably the table's name includesthe LSP's AECN. Each LSP's LRS routing table may be utilized for bothLRU and LRR. Each LSP's LRS routing table may include entries for allSSPs served by the ISCP in which the LSP's LRS routing table isinstalled. Conversely, any entry that an LSP has for all SSPs served bythe ISCP 30 must be in the same LRS routing table.

Referring now to FIG. 10, an exemplary ISCP logic architecture for LRUand LRR originating calls is described. Once an LSP has its LSP levelinformation setup for the area served by an ISCP 30, it is possible forthe LSP to place orders for ULS ports or resold lines for the same area.Lines require trigger CPRs 72 with some line specific variables. Thetrigger CPRs 72 connect to a feature interaction manager (FIM) CPR 74which connects to LRS service logic CPRs 76, 78 and other service logicCPRs 80. The trigger CPR 72 may consist of either trigger specificmodules or one default trigger module. In either case, only one logicblock exists within the trigger CPR 72 for a telephone number and thatlogic block must contain all modules. Both LRS CPRs 76, 78 communicatewith the LRS routing table 70 which receives information from the LSP asdiscussed above, and the local database table 54 for determining whethera call is local as discussed above.

Although FIG. 10 shows an OHD trigger, for centrex the OHD triggershould be replaced with a CDP-AC or CDP-IC trigger. For 5ESS PRI, theOHD trigger should be replaced with a PRI B-CH trigger. Although FIG. 10shows the LRU and LRR service logic as being separate, it is alsopossible to create a completely integrated logic, such as a combined CPRfor the operator and directory assistance components of LRS and aseparate CPR for the other traffic component of LRU. Alternatively, itis possible to separate or integrate the TAT and 10D logic modules forLRU terminating traffic (FIG. 11) with other LRS service logic modules.

FIG. 11 shows an ISCP logic architecture for LRU terminating calls. Thearchitecture is similar to the architecture shown in FIG. 10 but it issimpler, only requiring the trigger CPR 72, FIM CPR 74, LRU CPR 76 andother service logic CPRs 80.

For POTS, LRS utilizes both originating and terminating triggers on theSSP. LRS requires the triggers to be applied on a per telephone numberbasis. The OHD trigger is utilized on all switch ports which are beingsold on an unbundled basis to LSPs to provide routing service, ifdesired by the LSP, and to always create originating AMA records unlessthe 5ESS PRI switch is being utilized. For the 5ESS PRI switch, LRUutilizes a PRI B channel (PRIBC) trigger on all PRI switch ports whichare being sold on an unbundled basis to LSPs to provide routing service,if desired by the LSP, and to always create originating AMA records. LRUutilizes TAT or 10D triggers on all switch ports which are being sold onan unbundled basis to LSPs to always create terminating AMA records. LRRutilizes an OHD trigger on all switch ports which are being resold onother than an unbundled basis to LSPs to provide routing service, ifdesired by the LSP. But for 5ESS PRI, LRR will utilize a PRIBC triggeron all PRI switch ports which are being sold on other than an unbundledbasis to LSPs to provide routing service, if desired by the LSP. As aconsequence of the trigger requirements, LRU's OHD-PRIBC and TAT/10dtriggers always exist on all POTS switch ports which are being sold onan unbundled basis to LSPs because of billing. If a particular LCC isfor terminating only, the OHD/PRIBC trigger still exists in the ISCP,however, the trigger will not be utilized because no OHD/PRIBC triggeris in the SSP.

The LRR OHD/PRIBC trigger only exists if the LSP has active routingservice. If an LSP retailing lines bought wholesale from the incumbentLEC later decides to have active routing service, the ISCP would need,after establishing their LRS routing table, to have CPRs for each lineadded, and the SSPs would need to have a trigger set.

For centrex, LRS also utilizes both originating and terminating triggerson the SSP applied on a per telephone number basis. The followingtriggers are utilized on all switch ports which are being sold on anunbundled basis to LSPs to provide routing service, if desired by theLSP, and to always create AMA records for 9+ calls that escape outsidethe centrex: CDP-AC on the AXE-10, DMS-100 and 5ESS; and OHD on the1AESS. LRU utilizes the following triggers to create originating AMArecords for 2-6 digit station to station (intra-centrex) calls: CDP-ACon the 5ESS; and CDP-IC on the AXE-10, DMS-100, and 1AESS. LRU alwaysutilizes a TAT trigger on all switch ports being sold on an unbundledbasis to LSPs to always create terminating AMA records.

As a result of the centrex trigger requirements, LRU originatingtriggers exist for all standard LRS centrex calls on all centrex switchports which are being sold on an unbundled basis to LSPs. Moreover, LRUTAT triggers always exist on all centrex switch ports which are beingsold on an unbundled basis to LSPs. LRRs originating trigger for9+escape to the outside calls will only exist if the LSP has activerouting service. If an LSP retailing lines bought wholesale from theincumbent LEC later decide to have active routing service, the ISCPneeds, after establishing the LRS routing table, to have CPRs for eachline added and the SSP would need to have a trigger set.

LRU also requires an LRS_DMSDID provisionable call variable with ayes/no data type. Alternatively, a provisionable variable common tomultiple services, performing the same function, and kept in a datablock added to the trigger CPR when the first service of that group ofmultiple services is provisioned, may be utilized. When the LRUtelephone number is part of a DMS-100 DID trunk group, LRS_DMSDID, or analternative common variable, will be set to YES. When the service is LRRor an LRU for a telephone number that is not part of a DMS-100 DID trunkgroup, the LRS_DMSDID, or an alternative common variable, will be set toNO which is the default.

LRU also requires an LRS_DMSDID digit provisionable variable.Alternatively, a provisionable variable, in a multiple service,performing the same function, and kept in a data block added to thetrigger CPR 72 when the first service of that group or multiple servicesis provisioned, may be utilized. When the LRS_DMSDID is set to YES, thevalue of LRS_DMSDID digit, or the alternative common variable, will beset to 7 or 10 as required for that DMS-100 DID trunk group. WhenLRS_DMSDID is set to NO, the value of LRS_DMSDID digit, or thealternative common variable, will be set to 7, which is the default.

Another variable that may be utilized is the LRS_DMSDID trunkprovisionable variable. Alternatively, a provisionable variable, in amultiple service, performing the same function, and kept in a data blockadded to the trigger CPR when the first service of that group ofmultiple services is provisioned, may be utilized. When LRS_DMSDID isset to YES, the value of LRS_DMSDID trunk, or the alternative commonvariable, will be set to the routing index for that DMS-100 DID trunkgroup. When LRS_DMSDID is set to NO, the value of LRS_DMSDID trunk orthe alternative common variable, will be set to zero, the default value.

These provisionable variables must be part of the trigger CPR 72 for atelephone number with either LRU or LRR. All of the provisionablevariables should become a part of a data block. In a preferredembodiment, ISCP version 5.0 should be utilized. However, if a lowerversion such as ISCP version 4.3 is utilized, it is acceptable for thecalling scope and LSP provider variables to be part of either the logicblock or a common data block.

In order to facilitate LRS interaction with other AIN services, avariable may be provided which passes from the trigger CPR 72 to thefeature interaction manager CPR 74 indicating whether or not the LDB 54was utilized. If a LDB lookup was performed, the variable passes theresult so that the feature interaction manager CPR 74 can forward thatinformation on to other services, and potentially prevent superfluousLDB lookups.

The logic common to LRU and LRR is now described. The logic for operatorand directory assistance traffic (the traffic the two services have incommon) depends on a trigger such as an OHD, PRIBC or CDP-AC trigger.Initially, the LRS logic identifies 911 traffic based upon the digits911 input by the calling party. Although SSPs should have an OHDexclusion list which includes 911, 911 traffic is identified in the LRSlogic as a backup. For the CDP-AC triggered traffic, an equivalent 911exclusion list is within the ISCP to identify 911, and is therefore notmerely a backup. The LRS logic also identifies 10XXX traffic and routesit to an IXC switch because the calling party has made a deliberatedecision to utilize the dialed carrier.

The LRR logic then identifies seven digit local traffic based on thenumber of digits dialed by the calling party. The digits are returned tothe SSP as correctly dialed local traffic, and are never associated withoperator and directory assistance traffic. The LRS logic also identifiesinternational traffic, both direct dialed and operator dialed, andreturns it as correctly dialed international traffic to the SSP. The LRSlogic identifies 0+NPA-555-1212 dialed traffic based on the NXX-XXXXbeing equal to 555-1212, and returns it as correctly dialed traffic tothe SSP. The LRS logic determines if the 555-1212 traffic is local bylooking in the table within the ISCP which has a LATA for each callingparty and for each area code plus 555 per state.

The logic then determines whether all intra-LATA operator and directoryassistance calls should be routed to the LSP. If the determination isyes, first it is determined whether the NPA dialed is the same as thecalling number. If the NPAs are identical, the traffic is routed to theLSP. Otherwise, a lookup in the LATA table is made to see if the callednumber is in the same LATA as the calling number. If the called numberand calling number are within the same LATA, the traffic is routed tothe LSP. Otherwise, the traffic is routed normally, to an IXC.

The LRS logic also identifies 1+800-NXX-XXXX intra-LATA and inter-LATAtraffic, both direct dialed and operator, based on the NPA being equalto 800, 888, etc., and returns the called number to the SSP as correctlydialed traffic. Although the preceding and following descriptiondescribes the LRS logic as returning information directly to the SSP, infact, according to a preferred embodiment, the LRS logic first returnscontrol of the call to the FIM CPR 74, and the FIM CPR eventuallyreturns the response to the SSP.

The LRS logic identifies ten digit inter-LATA traffic, both directdialed and operator, based on the LATAs of the calling party and thecalled party not being equal. A lookup is done in the ISCP's LATA tableto determine the LATA of both the calling party and the called party. Ifthe LATAs are not equal, the traffic is determined as being inter-LATA,in which case it is returned as dialed to the SSP and validated ascorrectly dialed inter-LATA traffic.

The LRS logic also identifies ten digit intra-LATA operator dialedtraffic based on the LATAs of the calling party and called party beingequal per the ISCPs NPANXX table (local database) 54. The LRS logicsends the called number to the LDB 54 for a local versus tolldetermination based on the calling scope of the NPANXX of the callednumber. If the called number is identified as local by the LDB lookup,the LRS logic will then check for a routing index in the LRS routingtable 70 based on the value of the LSP provider variable. If the routingindex is found to exist and is not equal to the default routing index,the LRS logic returns the called number and routing index to the SSP. Ifno routing index is found in the table 70, or the routing index is equalto the default value, the ISCP tells the SSP to route to the dialednumber. If the called number is identified as a toll number by the LDB54, the LRS logic returns the called number to the SSP.

The LRS logic also identifies 411 and operator dialed 411 (0+411)traffic based on the NPA of the called number being equal to 411, andfor operator dialed 411 the NON being equal to operator. Once identifiedas direct dialed 411 or operator dialed 411, the LRS logic-checks for arouting index in the LRS table 70 based on the value of the LSP providervariable. If a routing index is found to exist and is not equal to thedefault, the LRS logic returns the routing index value from the LRSrouting table 70 to the feature interaction manager CPR 74. If the LRSrouting table 70 is checked and no routing index is found or the routingindex is equal to the default, the ISCP tells the SSP to route to thedialed number.

The LRS logic identifies operator dialed 311 (0+311) traffic based onthe NPA of the dialed number being equal to 311 and the NON being equalto operator. Once identified as operator dialed 311, the LRS logicchecks for the routing index in the LRS routing table 70 based on thevalue of the LSP provider and if the routing index is found to exist andis not equal to the default, the LRS logic returns the called number androuting index from the LRS table 70 to the FIM CPR 74. When the defaultrouting index or no value is found in the LRS routing table 70, the ISCPtells the SSP to route to the dialed number.

The LRS logic also identifies 00 dialed traffic based on the absence ofa value for the dialed number or the digits or value of 0 for the dialednumber. The DMS-100. shows one 0 in the dialed number when 00 is called.The other SSPs show no value for the dialed number. Once identified as a00 call, the ISCP tells the SSP to route to the dialed number.

The LRS logic identifies 0 dialed traffic based on the absence of avalue for the called number. Once identified as 0, the LRS logic checksfor a routing index in the LRS routing table 70 based on the value ofthe LSP provider. If the routing index is found to exist and is notequal to the default, the LRS logic returns the following information tothe FIM CPR 74: the called number, and the routing index value found inthe LRS routing table 70. The lookup in the LRS routing table 70 isdependent upon whether or not the end office is an AXE-10. If the endoffice is an AXE-10, the LRS routing table lookup may be based on theOPM value. If the end office is anything other than an AXE-10, thelookup can only be for the operator value. If there is no value or thevalue is the default value in the LRS routing table 70, the ISCP tellsthe SSP to route to the dialed number.

Now the logic unique to LRU is discussed. Once the logic common to LRUand LRR has been traversed, the only originating traffic left is 311,seven digit local, and ten digit intra-LATA direct dialed traffic. TheLSP may choose to have a trunk group from the originating SSP routed toa switch of their own for 311, seven digit local, and the local portionof the ten digit intra-LATA direct dialed traffic.

The LRU logic identifies seven digit 555-XXXX, 950-XXXX and 976-XXXXtraffic based on the number of dialed digits being seven and the NXXbeing 555, 950 or 976, respectively. Once identified, the LRU logicreturns the called number to the FIM CPR 74 to cause the traffic toutilize the incumbent LECs network. The LRU logic identifies seven digitlocal traffic based on the number of digits in the called number beingseven. Once it is identified as local, the LRU logic then checks for arouting index for local traffic in the LRU routing table 70 based on thevalue of the LSP variable, and if the routing index is found to existand is not equal to the default value, the LRU logic returns the callednumber to the FIM CPR 74 along with the value retrieved from the LRSrouting table. If the routing index is equal to the default value ordoes not exist, the ISCP tells the SSP to route to the dialed number.

The LRU logic also identifies ten digit intra-LATA direct dialed trafficbased on the LATAs of the called number and the calling party beingequal per the ISCP's LDB table 54. The LRU logic then forwards thecalled number to the LDB 54 for a local versus toll determination basedon the calling scope of the NPANXX of the called number. If the callednumber is identified as local by the LDB lookup, the LRU logic thenchecks for the routing index for local traffic in the LRS routing table70 based on the LSP variable for that calling party. If the routingindex is found to exist, and is not equal to the default, the callednumber along with the value obtained in the LRS routing table for localtraffic is forwarded to the FIM CPR 74. If there is no value in the LRSrouting table 70 or the value is equal to the default, then the ISCPtells the SSP to route to the dialed number. If the called number isidentified as a toll number by the LDB lookup, the ISCP tells the SSP toroute to the dialed number.

The LRU logic also identifies 311 direct dialed traffic with or withouta 1 prefix (because both are treated the same) based on the NPA of thecalled number being equal to 311. Once identified as 311 direct dialed,the LRU logic then checks for a routing index for local traffic in theLRS routing table 70 based on the LSP assigned to that calling party. Ifthe routing index is found to exist and is not equal to the defaultvalue, the LRU logic returns the called number and the value from theLRS routing table for local traffic to the FIM CPR 74. If no value isfound in the LRS routing table 70 or the default value is found, the LRSlogic returns the called number along with the default routing index tothe FIM CPR 74.

For 1AESS switches, 1+411 calls are not accepted/routed properly withLRU. Thus, in order to keep the directory assistance traffic on theincumbent LEC's network, a route index pointing to the LEC's directoryassistance trunk group is returned.

For terminating calls, the LRU logic has only one objective, cause abilling record to be created at the SSP for all terminating calls. Thus,LRU terminating logic tells the FIM CPR 74 that the call is cleared forcompletion to the called number. However, other services may divert thecalls to a telephone number other than the called number. The LRU logicreturns billing information to the FIM CPR 74.

The LRS should also be able to interact with other AIN services. Inorder for the interaction to occur, the LRS trigger must be integratedwith the other services trigger CPR 80. Moreover, the LRS logic is eveninvoked if a call to a terminating trigger is re-routed by another AINservice. That call may be redirected to a local number which requiresLRS routing (and originating billing).

For example, disaster routing service and intelligent redirect may beintegrated with LRS. Disaster routing allows a subscriber to predefinethree destination telephone numbers for each CDN in a group of CDNs andthen have one of those groups in effect. Thus, disaster routing allowsthe subscriber to reroute all calls to CDNs from one location to anotherlocation in the event the first location is lost because of a disaster.Intelligent redirect allows a subscriber to reroute all calls to CDNs atone location to another location based on various criteria such as timeof day. For example, all calls could route to a first number from 9:00am to 5:00 pm, and to another number at all other times. Because thedisaster routing service and intelligent redirect (DIF) are onlyinitiated via terminating triggers, LRR is inapplicable. However, LRUwhich does utilize terminating triggers for billing must be integrated.

The integration is via the feature interaction manager CPR 74. The FIMCPR 74 should receive variables back from DRF indicating whether or nota DRF billing record is to be generated, and the telephone number towhich the call is to be routed. The information will then be utilized byLRU in order to route the number to the proper destination, and togenerate a single billing record reflecting the LRU and DRF usage. Thefeature interaction manager may integrate features other than LRS withLRS by executing the other features first, and based upon the resultsreported to the feature interaction manager from the other features,executing the LRS logic.

Another exemplary feature which may interact with LRS is positive IDdescribed in U.S. patent application Ser. No. 09/050,986 to K. Krein etal., filed on Mar. 31, 1998, entitled “Profile Management SystemIncluding User Interface for Accessing and Maintaining Profile Data ofUser Subscribed Telephony Services”, which is herein expresslyincorporated by reference in its entirety. Positive ID determineswhether a calling party will be blocked from reaching the destinationnumber and accordingly has terminating call triggers. Positive ID doesnot require any billing and does not interact with LRU on that basis.However, positive ID can modify the LRU call processing record byblocking completion to the called number. Exemplary variables receivedby the feature interaction manager CPR 74 include a variable indicatingwhether or not the connection is authorized or whether a blockingannouncement is to be played. In response to the variables received frompositive ID, LRU directly interacts with positive ID on the terminatingtriggers and acts in accordance with the values in the variables.

While the invention has been described with reference to severalexemplary embodiments, it is understood that the words which have beenutilized are words of description and illustration, rather than words oflimitation. Changes may be made, within the purview of the appendedclaims, as presently stated and as amended, without departing from thescope and spirit of the invention in its aspects. Although the inventionhas been described with reference to particular means, materials andembodiments, the invention is not intended to be limited to theparticulars disclosed; rather, the invention extends to all functionallyequivalent structures, methods and uses, such as are within the scope ofthe appended claims.

1. A communication network element for routing communications from anoriginating connection address to a destination connection address overa network, the communication network element comprising: a receiverconfigured to receive a signal, comprising the originating connectionaddress and the destination connection address; a processor configuredto determine a service provider associated with at least one of theoriginating connection address and the destination connection address ofthe received signal, and to determine a routing preference associatedwith the service provider using routing data, and a service creatorconfigured to interact with a service management system to create and/ormodify a routing service application.
 2. The communication networkelement of claim 1, wherein the processor provides instructions forrouting the communications based on the determined routing preferences.3. The communication network element of claim 1, wherein the servicecreator loads the routing service application into a storage.
 4. Thecommunication network element of claim 1, further comprising: a memoryconfigured to store information used by the communication networkelement to determine whether the service provider has a routingpreference.
 5. The communication network element of claim 4, furthercomprising: a memory configured to store information that associates theservice provider with routing preference information.
 6. Thecommunication network element of claim 1, wherein the routing datafurther includes a variable that indicates an identity of the serviceprovider.
 7. The communication network element of claim 6, wherein thevariable is used to determine whether a local routing service routingtable is to be searched for a local routing index, comprising localdestination connection addresses.
 8. The communication network elementof claim 7, wherein the local routing service routing table includes alocal routing index comprising local destination connection addresses.9. A computer readable medium for storing a computer program, recordedon the computer readable medium and being executed by a computerprocessor, that enables communications to be routed from an originatingconnection address to a destination connection address over a network,the computer readable medium comprising: a receiving code segment,recorded on the computer readable medium, that receives a signal,comprising the originating connection address and the destinationconnection address; a determining code segment, recorded on the computerreadable medium, the determines a service provider associated with atleast one of the originating connection address and the destinationconnection address, a routing preference code segment, recorded on thecomputer readable medium, that determines a routing preferenceassociated with the service provider based on routing data, and aservice creator code element, recorded on the computer readable medium,that interacts with a service management system to create and/or modifya routing service application.
 10. The computer readable medium of claim9, further comprising: a storing code segment, recorded on the computerreadable medium, that stores information that associates the serviceprovider with routing preference information.
 11. The computer readablemedium of claim 10, wherein the routing data further includes a variablethat indicates an identity of the service provider.
 12. The computerreadable medium of claim 11, wherein the variable is used to determinewhether a local routing service routing table is to be searched for alocal routing index, comprising local destination connection addresses.13. The computer readable medium of claim 12, wherein the routingservice routing table includes a local routing index comprising localdestination connection addresses.
 14. The computer readable medium ofclaim 9, further comprising: a routing code segment, recorded on thecomputer readable medium, that provides instructions for routing thecommunications in accordance with the routing preference.
 15. A methodof routing communications from an originating connection address to adestination connection address, the method comprising: receiving asignal, comprising the originating connection address and thedestination connection address; determining a service providerassociated with at least one of the originating connection address andthe destination connection address; determining a routing preferenceassociated with the service provider using routing data; providinginstructions to route the communications in accordance with thedetermined routing preferences, and performing at least one of creatingand modifying a routing service application via an interface of aservice management system implemented on at least one computerprocessor.
 16. The method of claim 15, further comprising: storinginformation that associates the service provider with routing preferenceinformation.
 17. The method of claim 16, wherein the routing datafurther includes a variable that indicates an identity of the serviceprovider.
 18. The method of claim 17, further comprising: searching aservice provider table to determine the routing preference specified bythe service provider.
 19. The method of claim 18, wherein the serviceprovider table includes a unique routing index for specifiedcombinations of geographic areas associated with at least oneoriginating connection address and destination connection address. 20.The method of claim 15, further comprising: managing records for routedcommunications.